home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
pressgen
/
topiss.aug
< prev
next >
Wrap
Text File
|
1993-12-30
|
15KB
|
332 lines
NetWare OS
Q: The UNICODE diskette seems to hang the NetWare 3.12
installation of SYSTEM and PUBLIC files. Why is this
happening?
A: The UNICODE diskette takes longer to copy to the file server
than the other diskettes because it contains approximately 141
files. This set of 141 files is copied into the following
three separate locations during installation; SYS:SYSTEM\NLS,
SYS:LOGIN\NLS, and SYS:PUBLIC\NLS.
If the server is booted with DR DOS 6.0, the UNICODE
installation takes approximately 50 minutes. If the server is
booted with another version of DOS, the UNICODE installation
takes approximately 20 to 30 minutes. The machine type is
also a factor in the time required for the UNICODE diskette to
install.
The other diskettes have fewer files and are generally copied
to one subdirectory, so they only require very little time to
install.
Q: Are the NetWare 3.12 ElectroText manuals available to
download?
A: Yes. A copy of the manuals are in NW312D8.ZIP that is
available on the INTERNET on the FTP.NOVELL.COM server in the
PUB\DOCUMENTATION\CORPPUBS\NW312 directory.
Q: Where can I find the NetWare 3.12 Help command line utility?
A: The Help command line utility does not ship with NetWare 3.12.
Q: Does the CDROM "/R" parameter work?
A: No. This parameter only speeds up the CD MOUNT process by the
time it takes to build the DET and FAT databases in the system
subdirectory. The CDROM.NLM still requires a significant
amount of time to set up the tables in memory, depending on
the number and size of files on the CD-ROM itself.
The block size of the next release of the CDROM.NLM will be
changed from the current 4 KB to 64 KB, which will
significantly reduce the time it takes to mount a CD-ROM as a
NetWare volume.
Q: Will the CDROM.NLM mount a MAC or NFS CD-ROM?
A: No. The "/MAC" and "/NFS" parameters used with the CDROM.NLM
set up the cache tables in memory to make a regular CD-ROM
appear as a MAC or NFS volume, by adding the necessary DATA
and RESOURCE forks to the tables in memory.
Currently, Novell only supports the HFS CD format for
Macintosh. These CD-ROMs need to be mounted with the
HFSCDROM.NLM, which only ships with NetWare for Macintosh 4.x.
HFS CD-ROMs are not supported under NetWare 3.x.
Please note that when using the "/MAC" parameter, the message
stating that the volume is read only will appear every time
the CD-ROM is accessed because of a problem with AFP. Also,
the "/NFS" parameter does not work with the NetWare 4.x
version of CDROM.NLM. Novell is aware of these two problems,
which will be fixed with the next release of the CDROM.NLM.
Q: Will the READ ONLY messages that appear when mounting a CD-ROM
on a NetWare 4.x server ever be fixed?
A: Yes. These messages will be fixed in the next release of the
CDROM.NLM.
Q: What types of CD-ROM formats does CDROM.NLM support?
A: The CDROM.NLM supports two types of CD-ROM formats, the
ISO-9660 and the High Sierra format. At this time, however,
the CDROM.NLM is not properly supporting the High Sierra
format. Novell is aware of the problem and is working on a
solution.
Q: After upgrading to the latest 3C509.COM ODI driver, why do I
receive the "File Server Not Found" error?
A: The new ODI drivers default to the 802.2 frame type. When
using these drivers, you must use the 802.2 frame type on your
server or change the frame type for the workstation in the
NET.CFG (or SHELL.CFG) file.
Novell recommends changing the frame type at the server by
adding the frame= parameter to the Load LANDRIVER statement as
shown:
Load LANDRIVER Frame=Ethernet_802.2
MACINTOSH
Q: I have NetWare for Macintosh 3.011, and the ATPS print queues
always spool to the SYSTEM\ATPS subdirectory on the SYS:
volume. The volume is relatively small, and I am concerned
about having enough disk space. Can I change the place where
the queues spool?
A: Yes. When loading ATPS, use the -D parameter as shown:
LOAD ATPS -D VOL1:PRINT
If you use this parameter after the queues have already been
specified in SYS:SYSTEM\ATPS or another directory, you must
delete the existing queues in PCONSOLE for ATPS to create new
queues in the specified location.
Q: Is the DeskWriter 550C print driver supported in NetWare for
Macintosh?
A: The DeskWriter 550C driver is supported in NetWare for
Macintosh 4.01. However, NetWare for Macintosh 3.x shipped
before this driver was available, so it is not supported in
NetWare for Macintosh 3.x.
To work around the problem in NetWare for Macintosh 3.x, print
to a queue serviced by a 550C printer with the DeskWriter C
driver. Although this works, it does not take advantage of
the 550C printer's dual ink cartridge capabilities. For
details on how to do this, see the NetWare for Macintosh 3.12
"README" file.
Q: With NetWare for Machintosh 3.x, when printing to an ATPS
spooler using the Adobe Macintosh printer driver (also known
as PSPrinter, LaserWriter 8.0, or PostScript Level 2 driver),
why do Macintosh clients not receive all options or suffer
poor printing performance.
A: NetWare for Macintosh 3.x does not interpret PostScript Level
2 queries. One of the problems seen is that "all" fonts are
downloaded with each print job. Another problem seen is that
certain options like FAX printing may be unavailable. If this
problem causes difficulties, print directly to the printer or
go back to using the LaserWriter driver version 7.x or
earlier.
Q: Should I be concerned about the following message in my System
Log?
ATALK Warning: PAP connection 0xBB died due to tickle timeout
A: This message usually reflects a communications problem that
could be caused by faulty cabling or a bad routing path. One
or two messages a day is usually not a problem, because
printing can usually recover and continue. Seeing many of
these messages in a short time may indicate a more severe
problem that needs checking into.
To see if the problem is cable or routing related (for
example, external to the server), try moving the printer to a
cable segment directly attached to the server to see if the
problem is alleviated.
Any messages indicating low packet receive buffers or ECBs,
will require you to allocate more in the STARTUP.NCF file.
NetWare for Macintosh requires a minimum of 100 packet receive
buffers. For each additional bus mastering network board
(such as NE3200), add another 40 buffers. If you are not sure
what number this should be, check the documentation. The
Maximum Packet Receive buffers should be least 100 higher than
the Minimum Packet Receive buffers.
DRDOS
Q: Several games from MicroProse display errors that not enough
memory is available to run; however, the DOS command "MEM"
shows plenty of available memory. How can I fix this problem?
A: Update the DR DOS files to the 04-07-92 version (current
shipping version). You will also most likely need
PATCH326.ZIP from the Novell BBS at 408-649-3443 (2400 bps)
and 408-649-3696 (9600 bps). This patch is also available as
PAT326.EXE from your Novell Authorized Service Center (NASC),
Novell Reseller, or from one of Novell's electronic
distribution tools (for example, NetWire on CompuServe and the
Network Support Encyclopedia on CD-ROM).
NOTE: If you are experiencing any other problems besides
the one previously described, do not apply this
patch unless authorized by a Novell technician.
Q: I updated my computer's DR DOS 6.0 files with the 04-92
business update to allow DR DOS 6.0 and Windows 3.1 to run
together. Why do I still get the following error message
during the installation of Windows 3.1?
Standard mode fault in MS DOS extender wrong
A: This error usually happens if the workstations boot partition
is compressed with the DR DOS 6.0 SuperStor utility. The
computer boots from the uncompressed portion of this
partition; however, if the updated 04-92 system files and
memory manager were not updated on this partition the error
can occur. To check if this is the case, type the following
three commands at the root of the DOS prompt of the
uncompressed partition:
XDIR IBM*.*
XDIR COMMAND.COM
XDIR \DRDOS\EMM386.SYS
If any of these files do not exist or do not have the 04-92
file dates, use the update disk to update the host drive. For
example, if the D: drive is the uncompressed drive, then enter
UPDATE D: DRDOS from the floppy disk drive prompt where the
UPDATE disk is located.
Q: When trying to load certain applications, why do I receive the
error "!Packed file is corrupt"?
A: The first 64 KB of conventional memory is "low memory."
Traditionally, an operating system's code resides in this low
memory area. Today, however, DR DOS and most other DOS
operating system's code is relocated to the "high memory
area," to free up most of the 64 KB of low memory for use by
applications. Some applications that were coded using special
packing utilities to compress them, so they take up less room
on your disk drive, often become confused when they are loaded
into this low memory area, and they generate the error
message.
To correct this problem, use the MEMMAX -L command to disable
low memory before running the application. This can be done
in the AUTOEXEC.BAT file or a batch file that calls the
application (after exiting the application, use MEMMAX +L in
the batch file to enable the low memory again.)
Q: I receive an error indicating there is not enough disk space
when installing an application. However, a "DIR" of that
drive shows plenty of space. What is wrong?
A: Most likely, PENDING DELETE FILES are still being held on the
drive from using the DR DOS DELWATCH utility. Run CHKDSK to
get a report of the disk space being used by PENDING DELETE
FILES. If there are no previously deleted files you wish to
recover, type the following from the root directory of the
drive in question:
DELPURGE *.* /SA
For more information on PENDING DELETE FILES and DELPURGE, see
the DR DOS 6.0 User Guide.
NETWARE LITE
Q: How do I run a network copy of WordPerfect 6.0 (DOS or
Windows) under NetWare Lite?
A: You must "NET MAP" to a network directory that points to the
root of the server's hard disk. When WordPerfect 6.0
installs, several directories are created at the same level as
the main WP60 program directory. If you "NET MAP" to a
network directory that points directly to the WP60 directory,
WordPerfect 6.0 will not find the files needed to run.
Example:
If WordPerfect 6.0 is installed to C:\ (the root) on the
server, issue the following command:
NET MAP <drive letter> CDRIVE <server name>
Then go to that drive letter and type \WP60\WP. This allows
WordPerfect 6.0 to work across the network.
Q: I added a new computer to an existing NetWare Lite network
that has been working properly. The network software and
hardware are installed properly, yet this new machine is
unable to communicate with the others on the network. The
cabling is installed properly and to the correct
specifications. The network interface card is new, and it
does not conflict with any other components in the machine.
The card is using shared upper memory or a memory address
excluded with the upper memory manager in the CONFIG.SYS. Why
can't this machine see the others?
A: The network interface card may be defective. Also, check to
make sure the frame type matches the other machines.
To check the frame type, watch the network driver load to see
the frame type displayed. The Frame type is the format used
to package and send the information through the network cable
to the other systems. If the frame type is different from the
Frame type of other machines, they will not communicate.
If the frame type of the new machine is different than the
other machines, modify the NET.CFG file of the new computer
using a text editor. Add the following line under the Link
Driver heading as shown:
Link Driver
FRAME ETHERNET_802.3 (or 802.2 to match the others)
Reboot the system. The network card driver should load with
the same frame type as the other machines.
Q: Why does the I/O base address of 360h on a network interface
card conflict with LPT1 when the LPT1 I/O base address is
378h-37Fh?
A: Most network adapters use a 20h I/O address range, so the I/O
base address 360h occupies the range 360h-37Fh. Thus, the
network card address completely overlaps the LPT1 I/O base
address range.
Q: What is the minimum space SERVER.EXE needs to initialize?
A: SERVER.EXE requires more than 64,416 bytes but less than or
equal to 68,704 bytes to initialize, even if the server's
configuration is set to its minimum (approximately 33,488
bytes.)
For example, a server configured to use 40,000 bytes will
require approximately 68,704 bytes to initialize, but then it
shrinks back to 40,000 bytes. Any server configuration over
68,704 bytes will require approximately the same amount that
it estimates.
Q: If NetWare Lite is loaded, the Clipper application will only
open some of the files I need. For instance, I was trying to
open 47 files; however, it would only open 35 and then stop.
What could be causing this problem?
A: For this Clipper application, the DOS stacks command is
necessary. Add the following line to the CONFIG.SYS:
stacks=9,256